Skip to content

Instantly share code, notes, and snippets.

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

@jabbink
jabbink / Albert Heijn app API.md
Last active May 3, 2026 07:16
Interact with the Albert Heijn mobile app API to retrieve receipt data, and other things

AH API

Always use User-Agent: Appie/8.22.3 and Content-Type: application/json
Technically there is more information about your device and user ID after it, but the server does not seem to care

Token

If you have a valid access_token, add it as a header in request
Authorization: Bearer access_token

@lee-fuhr
lee-fuhr / statusline-README.md
Last active May 3, 2026 07:16
Claude Code statusline (Ghostty/tmux) — project-colored, quota display, session topics

Claude Code statusline

When you're running multiple Claude Code sessions — and you will be — the default experience gives you nothing. Every chat looks the same. You don't know what each one is doing. You don't know how much context is left before degradation kicks in. You don't know if you're about to hit your quota ceiling.

This statusline fixes that. One glance tells you what you're working on, where you stand, and whether you should wrap up. Each session is visually distinct. Nothing to configure, nothing to maintain.

image image
@MaheshPawaar
MaheshPawaar / Backend Engineering Fundamentals: The Master Checklist
Last active May 3, 2026 07:15
the 80/20 of backend engineering — 5 pillars, 45+ topics that cover 80% of what you'll actually use on the job. no fluff, no filler. study in order, check off as you go.
# Backend Engineering Fundamentals: The Master Checklist
## Pillar 1: The Internet & Communication
The foundational rules of how data moves across the web.
* **HTTP/HTTPS Lifecycle**
* **DNS Resolution:** How a domain name (like `google.com`) is translated into an IP address.
* **TCP Handshake:** The 3-way handshake (SYN, SYN-ACK, ACK) that establishes a reliable connection.
* **TLS/SSL Handshake:** How HTTPS encrypts data in transit to prevent packet sniffing.
* **The Request/Response Cycle:** The anatomy of an HTTP request (Method, Headers, Body) and response (Status Code, Headers, Body).
@huihut
huihut / Windows10-professional-activation.md
Created August 2, 2018 09:32
Windows10 专业版 激活方法
  1. 以管理员身份运行CMD
  2. slmgr.vbs /upk
  3. slmgr /ipk W269N-WFGWX-YVC9B-4J6C9-T83GX
  4. slmgr /skms zh.us.to
  5. slmgr /ato